Providing global accessibility to telehealth prescribed medications

ABSTRACT

Systems and methods for providing world-wide access to telehealth prescribed medications are provided. A patient prescription database receives electronic prescriptions from healthcare provider systems following telehealth consultations with patients by way of patient systems. Each electronic prescription is associated a unique patient identifier. Unique patient identifiers are received from pharmacy systems and the electronic prescriptions are retrieved from the patient prescription database for display. Following receipt of dispensation information from the pharmacy systems, the patient prescription database is updated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation in part of U.S. Non-Provisionalapplication Ser. No. 16/550,599 filed Aug. 26, 2019, the disclosures ofwhich are hereby incorporated by reference as if fully restated herein.

TECHNICAL FIELD

Exemplary embodiments relate generally to systems and methods forproviding global accessibility to telehealth prescribed medications.

BACKGROUND AND SUMMARY OF THE INVENTION

Accessibility to prescribed medications is difficult to obtain whentraveling. For example, one might leave for a trip and forget to packtheir medication, have their prescription stolen, lose theirprescription, or not realize that they only have a two-day supply leftin their current prescription, but they are scheduled to be gone for aweek. In such cases and others, it may be difficult to obtain neededmedications. Even where a prescription is available (new, refill, or thelike), it may not be desirable to fully transfer a prescription toanother pharmacy. In some cases, the transfer may take several days. Forexample, transferring pharmacies sometimes have little motivation tomove a prescription from their business such that transfers are a lowpriority item. Indeed, in some cases no refills are even left for apharmacy to act on. Getting in contact with the prescribing physician tohave a new prescription issued at a new pharmacy is time consuming andmay then require later transferring the new prescription back to theoriginal pharmacy. This difficulty is sometimes compounded by the factthat access to the medication may be critical to ensuring appropriatecare and continued health. As another example, an ongoing globalpandemic may leave a patient stranded in a remote location or otherwiserender an in-person consultation less than desirable. In such cases, aprescription (new, refill, or the like) may be difficult or impossibleto otherwise obtain.

Furthermore, the prescription and dispensation of medication is fraughtis fraud. Addicts will stop at little to obtain narcotics or othermedications. These addicts will often go so far as to fake symptoms andinjuries in the pursuit of drugs. While telemedicine is one way in whichpatients might remotely consult with a healthcare provider to obtainneeded prescriptions, refills, or the like, the remote nature oftelehealth consultation brings added risks for fraud. Besides fraud,mistakes and misunderstandings do occur regarding underlying symptoms,conditions, diagnoses, and the like which are used to justify aprescription. Gathering evidence to support prescription of medicationmay reduce the likelihood of fraud, mistake, and misunderstanding andprotect the patient and healthcare provider should such an accusationregarding the same be later made. Therefore, what is needed is a systemand method for providing global accessibility to evidence supported,telehealth prescribed medications.

Systems and methods for providing global accessibility to telehealthprescribed medications are disclosed herein. A patient may schedule aconsultation with a healthcare provider. The consultation may take placeby way of telephonic and/or videographic means, though such is notrequired. During or following the consultation, the healthcare providermay elect to prescribe one or more medications as part of a newprescription, a refill, or the like. Such prescriptions may be uploadedto a prescription database. In exemplary embodiments, the prescriptionsare coupled with evidence of the underlying disease, condition, orinjury observed or otherwise collected by the healthcare provider inconjunction with the consultation, though such is not required. Forexample, without limitation, the evidence may comprise photos of aninjury or other condition. Alternatively, or additionally, the evidencemay comprise test results, medical imaging results, self-reportedsymptoms, some combination thereof, or the like. The evidence may beuploaded to the patient prescription database and associated with theprescription.

The prescriptions may reside electronically on the prescriptiondatabase. The patient prescription database may be the only databasethat the prescriptions may reside on during their existence, though suchis not necessarily required. The patient prescription database may beelectronically partitioned so as to provide a private, virtual storagevault for the patient's prescription(s). For example, each of thepatient's prescriptions may be contained with a partitioned area of thepatient prescription database such that the area is not shared withother patients. The uploaded evidence may be associated with theprescription and be contained within the partitioned area such that theevidence is not shared with other patients, though such is not required.In exemplary embodiments, the prescribing healthcare provider may uploada prescription directly to the patient's partitioned area within thepatient prescription database and the prescription may be removed oncedispensed or expired. In exemplary embodiments, a unique prescriptionidentifier may be associated with each prescription uploaded to theprescription database.

The evidence may be directly uploaded, though such is not required. Inexemplary embodiments, the evidence may remain within the partitionedarea or otherwise for a period of time or indefinitely. The evidence maybe retrieved when the prescription is accessed to verify the patient'sidentity. For example, the evidence may show a broken arm and checkedagainst the appearance of the alleged patient for identity verification.Alternatively, or additionally, the evidence may be accessed to comparea patient's current presentation of symptoms, injury, condition,disease, or the like with a former presentation for purposes ofevaluating the adequacy of a prescription, the potential for fraud, theneed for a refill, the need for further treatment, some combinationthereof, or the like. For example, the prescription of a significantamount of powerful narcotic against a relatively minor injury maytrigger the dispensing pharmacist to verify the amount, type, or thelike of medication prescribed to treat the underlying alleged pain orotherwise flag the prescription as potentially mistaken, fraudulent, orthe like.

The patient prescription database may comprise one or more of: a numberof prescriptions, a list of unique patient identifiers, a list of uniquepharmacist identifiers, and a list of unique healthcare providers. Thedatabase may be contained within a single electronic storage device orspread across multiple, locally or remotely located electronic storagedevices. Identification information may be stored at the patientprescription database and associated with various patient identifiers.Upon receipt of a patient identifier at a pharmacy system, the patientprescription database may be queried to retrieve information associatedwith the received unique patient identifier. The information maycomprise identification information, prescription information, evidence,some combination thereof, or the like. The information may be sent tothe pharmacy system for display.

Alternatively, or additionally, identification information may beentered at the pharmacy system and a match determination may be madeagainst the identification information stored at the patientprescription database for the associated patient identifier. Inexemplary embodiments, the identification information may take the formof an identification device, code, password, biometric information, somecombination thereof, or the like issued to the patient followingenrollment. The identification device may comprise a chip or otherstorage device comprising the unique patient identifier and variousunique prescription identifiers associated with the patient. Theidentification device may be presented to the pharmacist for reading atthe pharmacy system.

Prescriptions associated with the received unique patient identifier maybe displayed. One or more of the displayed prescriptions may beselected. Dispensation information, including an amount of medicationdispensed, a time and date of dispensation, and a reason fordispensation may be received and updated at the prescription database.The reason for dispensation may be selected from a predetermined list ofreasons such as, but not limited to: lost prescription, not enoughmedication left, theft of medication. Evidence associated with thereceived unique patient identifier may be displayed. Alternatively, oradditionally, the evidence may be retrieved based on its associationwith retrieved or otherwise accessed prescriptions.

Patients may be provided with read-only access to certain informationstored at the patient prescription database associated with an enteredunique patient identifier. Such information may include a list of theprescribed medications, evidence, some combination thereof, or the like.Patients may be provided with access by way of a patient system.

Healthcare providers may be provided with write-access to certaininformation stored at the patient prescription database associated withan entered unique healthcare provider identifier. Healthcare providersmay be provided with access by way of a healthcare provider system. Suchwrite-access may be limited to the prescription information and/orevidence, except the dispensation information, which may be provided asread-only or not provided at all.

Pharmacists may be provided with write-access to certain informationstored at the patient prescription database associated with an enteredunique pharmacist identifier. Pharmacists may be provided with access byway of a pharmacy system. Such write-access may be limited to thedispensation information. Other information, such as a list ofprescriptions associated with an entered unique patient identifierand/or evidence, may be provided read-only.

Each unique pharmacist identifier may be associated with a geographicarea. Translation of prescription information may be provided based uponthe geographic area associated with an entered unique pharmacistidentifier. Furthermore, geographic specific brand names and/or genericnames may be retrieved for display based upon the geographic areaassociated with the received pharmacist identifier.

In exemplary embodiments, prescription information from the patientprescription database may only be viewed and/or edited upon successfulentry of identifiers from the patient and one or more of: a pharmacist,healthcare provider, and system administrator. In this way, the patientprescription database may require a double verification system. Theidentifiers may take the form of, for example without limitation,passwords, codes, biometric information, electronic keys, alphanumericsequences, some combination thereof, or the like. The identifiers may beunique. The identifiers may be of the same or different type for eachindividual.

In exemplary embodiments, the patient prescription database may beconfigured to release a copy of, order for, data regarding, somecombination thereof, or the like for one or more prescriptions for agiven patient based on user provided information. The pharmacy database,and/or related systems, may be configured to display pharmaciesgeographically proximate a given location and may be further configuredto indicate whether the prescribed medication is in stock and/or howlong the patient's expected wait time for the prescription may be.Alternatively, or additionally, the patient prescription database and/orrelated systems may be configured to indicate delivery servicesavailable for the given prescribed medications. In exemplaryembodiments, only a single fill of a prescription may be released at agiven time.

In exemplary embodiments, the patient prescription database and/orrelated systems may be configured to indicate when the patients' supplyof a given medication is expected to be low or out, when a refill isavailable, some combination thereof, or a like. The patient prescriptiondatabase or related systems may be configured to notify the patientand/or schedule or provide a listing of available telemedicineappointments.

Further features and advantages of the systems and methods disclosedherein, as well as the structure and operation of various aspects of thepresent disclosure, are described in detail below with reference to theaccompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

In addition to the features mentioned above, other aspects of thepresent invention will be readily apparent from the followingdescriptions of the drawings and exemplary embodiments, wherein likereference numerals across the several views refer to identical orequivalent features, and wherein:

FIG. 1 is a plan view of an exemplary system;

FIG. 2A is a simplified block diagram illustrating exemplary logic fordispensing a prescription using the system;

FIG. 2B is a simplified block diagram illustrating other exemplary logicfor dispensing a prescription using the system;

FIG. 3 is a simplified block diagram illustrating exemplary logic forentering a new prescription into the system;

FIG. 4 is a simplified block diagram illustrating exemplary logic foradding a new user to the system;

FIG. 5 is an exemplary identification device;

FIG. 6 is a plan view of an exemplary telehealth embodiment for use withthe systems and methods of FIGS. 1-5;

FIG. 7 is an exemplary pharmacy selection user interface for use withthe systems and methods of FIGS. 1-6; and

FIG. 8 is a plan view of an exemplary appointment scheduling interfacefor use with the systems and methods of FIGS. 1-7.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENT(S)

Various embodiments of the present invention will now be described indetail with reference to the accompanying drawings. In the followingdescription, specific details such as detailed configuration andcomponents are merely provided to assist the overall understanding ofthese embodiments of the present invention. Therefore, it should beapparent to those skilled in the art that various changes andmodifications of the embodiments described herein can be made withoutdeparting from the scope and spirit of the present invention. Inaddition, descriptions of well-known functions and constructions areomitted for clarity and conciseness.

Embodiments of the invention are described herein with reference toillustrations of idealized embodiments (and intermediate structures) ofthe invention. As such, variations from the shapes of the illustrationsas a result, for example, of manufacturing techniques and/or tolerances,are to be expected. Thus, embodiments of the invention should not beconstrued as limited to the particular shapes of regions illustratedherein but are to include deviations in shapes that result, for example,from manufacturing.

FIG. 1 is a plan view of an exemplary system 10. The system 10 maycomprise a patient prescription database 12. The patient prescriptiondatabase 12 may be in electronic communication with one or more pharmacysystems 16. The patient prescription database 12 may be in electroniccommunication with one or more patient systems 18. The patientprescription database 12 may be in electronic communication with one ormore healthcare provider systems 20. Such electronic communication maybe made by way of one or more networks 14.

The patient prescription database 12 may comprise one or more databases,servers, processors, electronic storage devices, some combinationthereof, or the like. The patient prescription database 12 may,alternatively or additionally, comprise one or more cloud-based storagesystems. The patient prescription database 12 may comprise one or moredevices housed at a single location or distributed amongst multiplelocations.

Each pharmacy system 16 may be associated with one or more pharmacists,pharmacies, some combination thereof, or the like. Each pharmacy system16 may comprise one or more electronic devices such as, but not limitedto, personal computers, laptops, tablet computers, smartphones,smartwatches, servers, processors, electronic storage devices, somecombination thereof, or the like. Each pharmacy system 16 may comprisethe same or different components. Each patient system 18 may beassociated with one or more patients and may comprise one or moreelectronic devices such as, but not limited to, personal computers,laptops, tablet computers, smartphones, smartwatches, servers,processors, electronic storage devices, some combination thereof, or thelike. Each patient system 18 may comprise the same or differentcomponents. Each healthcare provider system 20 may be associated withone or more healthcare providers, offices, some combination thereof, orthe like. Each healthcare provider system 20 may comprise one or moreelectronic devices such as, but not limited to, personal computers,laptops, tablet computers, smartphones, smartwatches, servers,processors, electronic storage devices, some combination thereof, or thelike. Each healthcare provider system 20 may comprise the same ordifferent components. The network(s) 14 may comprise one or moreinternets, intranets, the world wide web, cellular networks, wirednetworks, wireless networks, LANs, some combination thereof, or thelike.

FIG. 2A is a simplified block diagram illustrating exemplary logic fordispensing a prescription using the system 10. An individual may haveone or more prescriptions stored at the patient prescription database12. In exemplary embodiments, the prescriptions are stored in electronicform. Such electronic prescriptions may include scanned or other imagesof handwritten prescriptions, but preferably include e-prescriptiondocuments, data, or information. By way of illustration, withoutlimitation, the individual may have packed for a seven-day cruise onlyto realize that he or she only has two days' worth of their importantheart medication left. The individual may visit the ship's pharmacy tohave additional medication dispensed using the system 10. Beforedispensing the prescription, the identity of the individual may first beverified.

The individual may identify himself or herself to the pharmacist orother pharmacy team member. The individual may provide a unique patientidentifier for the pharmacy team member to enter into the pharmacysystem 16, though such is not required. In other exemplary embodiments,the individual may provide the unique patient identifier at the patientsystem 18.

Alternatively, or additionally, the individual may provide one or moreforms of identification to verify that they are who they say they are.Such identification may comprise, for example without limitation, aphoto identification, a government issued driving license, a governmentissued passport, a credit card, a utility bill, some combinationthereof, or the like. Such information may be provided manually, orelectronically, such as by upload to the pharmacy system 16 and/or thepatient system 18. In exemplary embodiments, the pharmacy team membermay enter the information at the pharmacy system 16. The information maybe entered manually at the pharmacy or patient systems 16, 18, or by wayof one or more peripheral devices 22. The peripheral devices 22 mayinclude, for example without limitation, magnetic strip readers, chipreaders, imaging devices, cameras, scanners, RFID devices, QR readers,barcode scanners, fingerprint readers, biometric information gatheringdevices, some combination thereof, or the like. In exemplaryembodiments, the presented forms of identification may be stored at thepatient prescription database 12 in conjunction with the transaction forlater review.

The entered information may be compared with identification informationstored at the patient prescription database 12 to determine if theentered information matches the information stored at the patientprescription database 12. In exemplary embodiments, the patientprescription database 12 may be configured to compare an entered uniquepatient identifier against patient identifiers stored at the patientprescription database 12. Alternatively, or additionally, the patientprescription database 12 may be configured to compare other enteredidentification information against stored identification informationassociated with a provided unique patient identifier. In other exemplaryembodiments, the entered identification information may be comparedagainst all stored identification information to determine the presenceor non-presence of a match.

The match determination may be performed electronically at the patientprescription database 12, though it is contemplated that such matchingmay instead be performed at the pharmacy system 16 and/or the patientsystem 18. For example, without limitation, a magnetic strip associatedwith the driver's license may be read and electronically compared forstored information at the patient prescription database 12.

If no matching information is found, such information may be displayedat the pharmacy system 16 and/or the patient system 18. If a match isfound, such information may be displayed at the pharmacy system 16and/or the patient system 18. Where a match is found, additionalfeatures or information may be accessed and/or further steps permittedas shown and described herein. Where no match is found, access to suchadditional features or information and/or further steps may be denied.

In other exemplary embodiments, stored identification informationassociated with an entered unique patient identifier may beelectronically transmitted from the patient prescription database 12 tothe pharmacy system 16 for manual review by the pharmacy team memberagainst the provided identification. Such stored identificationinformation may comprise, for example without limitation, images ofvarious forms of identification, biometric data, patient images, somecombination thereof, or the like.

The identification of the dispensing pharmacist and/or pharmacy may beverified. The pharmacy team member may enter a unique pharmacistidentifier at the pharmacy system 16. This unique pharmacist identifiermay only be provided to pharmacy team members acting under a verifiedpharmacy license as further described herein. The entered uniquepharmacist identifier may be evaluated against unique pharmacistidentifiers stored at the patient prescription database patientprescription database 12 to determine if a match exists. The presence ornon-presence of a match may be displayed at the pharmacy system 16.Where a match is found, additional features or information may beaccessed and/or further steps permitted as shown and described herein.Where no match is found, access to such additional features orinformation and/or further steps may be denied. In this way, both thepatient's identification and the dispensing pharmacy's and/orpharmacist's identification may be verified prior to access toprescription information stored at the patient prescription database 12.

Alternatively, or additionally, identification of the prescribinghealthcare provider and/or office may be verified. The healthcareprovider team member may enter a unique healthcare provider identifierat the healthcare system 20. This unique healthcare provider identifiermay only be provided to healthcare provider team members acting under averified healthcare provider license as further described herein. Theentered unique healthcare provider identifier may be evaluated againstunique healthcare provider identifiers stored at the patientprescription database 12 to determine if a match exists. The presence ornon-presence of a match may be displayed at the healthcare providersystem 20. Where a match is found, additional features or informationmay be accessed and/or further steps permitted as shown and describedherein. Where no match is found, access to such additional features orinformation and/or further steps may be denied. In this way, both thepatient's identification and the prescribing healthcare provider'sand/or office's identification may be verified prior to access toprescription information stored at the patient prescription database 12.

A similar technique may be used to verify the identification of one ormore system administrators.

In exemplary embodiments, prescription information from the patientprescription database 12 may only be viewed and/or edited uponsuccessful entry of identifiers from the patient and one or more of: apharmacist, healthcare provider, and system administrator. Suchidentifiers may be provided by way of respective systems 16, 18, and/or20. In this way, the patient prescription database may require a doubleverification system. The identifiers may take the form of, for examplewithout limitation, passwords, codes, biometric information, electronickeys, alphanumeric sequences, some combination thereof, or the like. Theidentifiers may be uniquely assigned and maintained. The identifiers maybe of the same or different type for each individual or entity.

Upon a successful double verification, access to the individual'savailable prescriptions as listed in the patient prescription database12 may be generated for display at one or more relevant systems 16, 18,and/or 20. All prescriptions available may be displayed. Expiringprescriptions may be automatically deleted from the patient prescriptiondatabase 12. Furthermore, prescriptions and accounts associated with oneor more individuals, medical care professionals, pharmacy team members,or other users who have not paid a service fee may be automaticallydeleted. The patient prescription database 12 may be configured toattend to such management efforts automatically. Alternatively, oradditionally, one or more administrators may be granted write-access tomake such changes manually.

In exemplary embodiments, without limitation, the unique pharmacistidentifier may be associated with one or more languages. Theprescription information may be automatically translated, by way of ahuman or machine translation, into the associated language. Suchtranslation may be performed by way of a translation module 24 inelectronic communication with the patient prescription database 12. Inother exemplary embodiments, the translations may automatically beperformed when the prescription entry is created within the system 10,and the appropriate translation may be retrieved and displayed.

The unique pharmacist identifier may be associated with one or moregeographic areas. The patient prescription database 12 may be configuredto associate each prescription with various equivalents, alternatives,generics, and the like for each geographic area. For example, withoutlimitation, a prescription for a brand name drug may be written andinitially dispensed from a pharmacy associated with the United Statesunder the brand name marketed in the United States. However, Europe mayhave access to different equivalent or alternative drugs than the UnitedStates. Alternatively, or additionally, Europe may have the same drugmarketed under a different brand or generic name. The patientprescription database 12 may be configured to automatically retrieve thebrand name equivalent, alternatives, or generics available in thegeographic area associated with the unique pharmacist identificationcode, which may or may not be available in all geographic areas. Inexemplary embodiments, such language and/or geographic areas associationmaybe automatically determined, or verified, by the IP address of thepharmacy system 16.

Dispensing information for each prescription may be entered at thepharmacy system 16. Such dispensing information may include the identityof medications dispensed, time and date of dispensation, how many unitsof medication were dispensed (e.g., number of tablets, number ofmilliliters, etc.), some combination thereof, or the like. Suchdispensing information may, alternatively or additionally, comprise areason for dispensing, which may be a mandatory entry. The reason may beselected from a predetermined list of reasons such as, but not limitedto: lost prescription, not enough medication left, or theft ofmedication. The patient prescription database 12 may be configured toautomatically update appropriate prescriptions saved at the database 12in accordance with such received information.

The patient prescription database 12 may be configured to automaticallyflag users as potentially fraudulent who request dispensation a certainnumber of times within a certain time period and/or a particular reasonfor dispensation with a frequency above a predetermined threshold. Soflagged users may be required to provide additional documentation suchas, but not limited to, an affidavit, police report, statement fromhealthcare provider, some combination thereof, or the like. In otherexemplary embodiments, some flagged users may have their relatedprescriptions, or all prescriptions, deleted from the patientprescription database 12, or may be otherwise prevented from obtainingadditional medications using the system 10. In exemplary embodiment, thedispensation of each medication may be recorded by way of one or moreelectronic receipts stored at the patient prescription database 12.

In exemplary embodiments, only a portion of the prescribed medicationmay be dispensed. For example, just enough to get the user through theirimmediate needs until they can return to their regular pharmacy may beprovided. If a user is traveling on a seven-day cruise and only has twodays' worth of medication, for example without limitation, only fivedays' worth of medication may be dispensed. The pharmacy team member maybe required to enter such information as part of the dispensinginformation. For example, without limitation, the pharmacy team membermay be required to provide a detailed explanation for the number ofunits of medication dispensed for storage at the patient prescriptiondatabase 12. The explanation may be associated with the dispensation. Inthis way, the individual's story may be subsequently verified by traveldocuments, credit card purchases, receipts, passport entries, somecombination thereof, or the like.

The amount of medication dispensed, whether a full or partial refill, orthe like, may be noted at the patient prescription database 12 andeffectively subtracted from remaining available refills, amount ofmedication, or the like in some cases, such as where the patientindicates they ran out of medication. In other cases, the amount ofmedication dispensed may not be so subtracted, such as where the patientindicates that the medication was lost or stolen.

Any examples or scenario shown and/or described herein are merelyexemplary and are not intended to be limiting. The system and methodsdescribed herein may be utilized to fill any number and type ofprescriptions such as entire prescription's, new prescriptions, refills,some combination thereof, or the like. In exemplary embodiments, certainmedications, or classes of medications, such as but not limited tonarcotics, may be restricted from partial fulfilment by the patientprescription database 12. Such restrictions may be geographic specific.

In exemplary embodiments, the patient prescription database 12 may be inelectronic communication with a telehealth module 42. The telehealthmodule 42 may be configured to facilitate telemedicine visits between apatient and the healthcare provider. Such telemedicine visits mayinclude telephonic calls, VOIP calls, video conferencing sessions,text-based exchanges, some combination thereof, or the like. Inexemplary embodiments, a patient may elect to participate in atelehealth visit by way of their patient system 18 and/or such atelehealth visit may be required prior to filling or re-filling theprescription in question. Upon receipt of such a request, the telehealthmodule 42 may be configured to automatically distribute a text message,email, scripted phone call, or other electronic notification to a numberof enrolled healthcare providers, by way of the respective healthcareprovider systems 20. A healthcare provider may accept the telemedicinerequest. After the telemedicine experience has been completed, thepatient prescription database 12 may be configured to distribute paymentto the healthcare providers. The amount disbursed may be automaticallybilled to the patient and/or his/her insurance provider. The telehealthmodule 42 may alternatively, or additionally, be configured tofacilitate in person visits, such as but not limited to, by coordinatinga time, place, and healthcare provider for the visit.

An exemplary user interface 52 at an exemplary patient system 18 isshown at FIG. 8. An electronic notification may be automaticallygenerated and displayed at the patient system 18 by the patientprescription database 12 and/or the telehealth module 42 asprescriptions run low, become expired, or the like. The notification maycomprise a prompt for scheduling telemedicine providers. The prompt maycomprise a listing of available or descried appointments, such asvarious dates and times. In other exemplary embodiments, the system maybe configured to match patients with available, nearby healthcareproviders for an in-person visit.

The patient prescription database 12 may be in electronic communicationwith an on-call pharmacist module 44. The on-call pharmacist module 44may be configured to automatically distribute a text message, email,scripted phone call, or other electronic notification to a number ofenrolled pharmacists by way of the pharmacy systems 16. A patient mayrequest an on-call pharmacist by way of the patient system 18. Theon-call pharmacist module 44 may be configured to match patients withon-call pharmacists located nearby to dispense a prescription. Apharmacist may accept the on-call request. After the prescription isfilled, the patient prescription database 12 may be configured todistribute payment to the pharmacist. The amount disbursed may beautomatically billed to the patient and/or his/her insurance provider.

The payments and billing discussed herein may be accomplished by way ofa billing module 46 in electronic communication with the patientprescription database 12, though such is not required. The billingmodule 46 may be configured to automatically generate and transmitrequests for reimbursement to insurance providers, generate and transmitinvoices to the patient, electronically disburse payments to providers,some combination thereof, or the like.

FIG. 3 is a simplified block diagram illustrating exemplary logic forentering a new prescription into the system 10. A healthcare providermay initiate a new prescription within the patient prescription database12 at a healthcare provider system 20. The healthcare provider may entera unique healthcare provider identifier. The healthcare provider mayenter prescription information. Such prescription information mayinclude, for example without limitation, the name of the medication, thedosage schedule, the amount of medication to be provided, the number ofrefills available, some combination thereof and the like. In exemplaryembodiments, the prescription information may further comprise anexpiration date for each prescription. If such information is notprovided, the patient prescription database 12 may automatically entersuch expiration information. The expiration information may beautomatically determined based on the classification of the drugprescribed. Table 1 provides an exemplary list, without limitation, ofdefault expiration time tables for classes of drugs.

TABLE 1 Class of Drug Default Expiration Narcotic 1 month Antibiotic 6weeks Mood-altering drug 2 months Over the counter 1 yearTable 1 is provided as an example, without limitation. Any defaultexpiration time for any type or class of drug is contemplated. Thedefault expiration may be specific to the geographic region associatedwith the prescribing healthcare provider and/or the disbursing pharmacy.In exemplary embodiments, the patient prescription database 12 may beconfigured to automatically set the geographically relevant expirationdata based on the location of the prescribing healthcare provider and/orthe disbursing pharmacy.

Upon expiration, the prescription may be automatically removed from thepatient prescription database 12. The patient prescription database 12may be configured to find equivalent name brand and/or generic drugsassociated with a prescribed medication for each geographic area basedon information stored at the patient prescription database 12 orelsewhere. The patient prescription database 12 may be configured toautomatically translate the prescription information into a number oflanguages by way of a human or machine translator, such as by way of thetranslation module 24.

In exemplary embodiments, a unique prescription identifier may beassociated with each prescription uploaded to or otherwise stored at thepatient prescription database 12. The unique identifiers describedherein may be generated and assigned by a unique identifier module 28which may be configured to create such unique identifiers. The uniqueidentifier module 28 may be in electronic communication with the patientprescription database 12.

Each unique prescription identifier may be stored at the patientprescription database 12 in a list. Each unique prescription identifiermay be associated with one or more unique patient identifiers associatedwith the patient for whom the prescription is written. Each uniqueprescription identifier may be associated with one or more uniquehealthcare provider identifiers associated with the prescribinghealthcare provider. The unique prescription identifier may be entered,for example without limitation, by way of one or more of the pharmacysystems 16, the healthcare provider systems 20, and/or the patientsystems 18 and the appropriate prescription information may be returned.

As shown in FIG. 2B, a prompt to enter the unique prescriptionidentifier may be generated. Upon entry, a determination may be made asto whether the entered unique prescription identifier matches one of theunique prescription identifiers stored at the patient prescriptiondatabase 12. This may provide an additional layer of verification.First, the entered unique prescription identifier must match one storedat the patient prescription database 12. Second, the unique patientidentifier associated with the matched unique prescription identifier asstored at the patient prescription database 12 may be retrieved andcompared to the entered patient identifier to determine a match.

FIG. 4 is a simplified block diagram illustrating exemplary logic foradding a new user to the system 10. An application for a new user may bereceived. The application may indicate whether the user is a patient,pharmacist, healthcare provider, or administrator. Each user may be tiedto a unique identifier. The unique identifiers may be segregated bytype: patient, pharmacist, healthcare provider, or administrator, thoughsuch is not required. The unique identifier may be provided only uponthe provision, storage, and verification of certain identificationinformation. A patient user may be required to provide one or more formsof identification. Such identification may comprise, for example withoutlimitation, a photo identification, a government issued driving license,a government issued passport, a credit card, a utility bill, somecombination thereof, or the like. Upon provision of such information,the patient user may be issued a unique patient identifier. Entry of theunique patient identifier, for example at the patient system 18, maygrant the patient read-only access to certain information stored at thepatient prescription database 12 and associated with the entered uniquepatient identifier. Such information may comprise the list ofprescriptions associated with the unique patient identifier. In thisway, the user may be able to retrieve and view prescriptions available.

New pharmacy users may be required to provide one or more licenses orcertifications such as, but not limited to, DEA certificates orequivalent government licensure for the geographic region the pharmacyoperates in. Other certifications, licensures, or the like associatedwith the pharmacist's licensure to dispense certain medications may beprovided. The pharmacist associated with a unique pharmacist identifiermay be held responsible for any and all medications dispensed under theunique pharmacist identifier.

New healthcare provider users may be may be required to provide one ormore licenses or certifications such as, but not limited to, medicallicenses or equivalent government licensure for the geographic regionthe medical professional operates in. Other certifications, licensures,or the like associated with the healthcare provider's licensure toprescribe certain medications may be provided. The healthcare providerassociated with a unique healthcare provider identifier may be heldresponsible for any and all medications dispensed under the uniquehealthcare provider identifier.

New administrator users may be required to provide one or morecertifications for access. The administrator associated with a uniqueadministrator identifier may be held responsible for any and all changesmade under the unique administrator identifier.

The patient prescription database 12 may be configured to receive aunique identifier and check for the presence or non-presence of such aunique identifier at the patient prescription database 12. Uniqueidentifier associated with a patient user may be granted read-onlyprivilege as to prescriptions associated with an entered unique patientidentifier. Unique identifiers associated with a pharmacy user may begranted write-privileges as related to the dispensing of medications.Unique identifier associated with a healthcare provider may be grantedwrite-privileges as related to the generation of prescriptions. Thepatient prescription database 12 may further comprise a list of activeusers, who may be associated with users who have paid a service fee.When a service fee goes unpaid, the associated unique identifier may beremoved from the list, or other action may be taken such that the usermay no longer be able to access the patient prescription database 12.

Such service fees may be received by way of a payment module 26, thoughsuch is not required. The payment module 26 may be configured to receivepayment information indicating the receipt of service fees. Such paymentmay be processed by way of credit card transactions, debit cardtransactions, bank transfers, electronic checks, some combinationthereof, or the like.

The unique identifiers shown and/or described herein may comprise, forexample without limitation, codes, alphanumeric identification, user id,passwords, digital certificates, facial recognition data, finger printdata, or other biometric information, one-time access codes, somecombination thereof, or the like. Each unique identifier may indicateone or more points of information about the underlying patient,prescription, healthcare provider, pharmacist, and/or administrator. Forexample, without limitation, a digit in the unique identifier maycorrespond with a particular geographic limitation. Another digit maycorrespond with a class of drug. These are merely exemplary and are notintended to be limiting.

The prescriptions and/or data related to the same (e.g., images thereof,e-prescription data, certifications, some combination thereof, or thelike), which may be generally referred to herein as prescription(s), mayreside within the patient prescription database 12. The patientprescription database 12 may be the only database that the prescriptionsreside on during their existence, though such is not required. Thepatient prescription database 12 may be electronically partitioned so asto provide a private, virtual storage vault for the patient'sprescription. For example, each patient's prescription(s) may becontained with a partitioned area of the patient prescription database12 such that the area is not shared with any other patients. Inexemplary embodiments, the prescribing healthcare provider may upload aprescription directly to the patient's partitioned area within thedatabase 12 and the prescription may be removed once dispensed orexpired. The data residing within a given one of the partitioned areas,in exemplary embodiments, may only be viewed and/or modified upon dualverification such as, but not limited to, by way of entry andverification of a unique patient identifier and one or more of: a uniquehealthcare provider identifier, a unique pharmacist identifier, and aunique administrator identifier.

FIG. 5 is an exemplary identification device 30. In exemplaryembodiments, the identification information described herein may takethe form of an identification device 30 issued to the patient afterenrollment. The identification device 30 may comprise a chip 32,magnetic strip, some combination thereof, or the like comprising theunique patient identifier and various unique prescription identifiersassociated with the patient. Electronic copies of various identificationdocuments may be stored at the chip 32 for manual comparison topresented documents. An identification device 30 may be issued topatient after successful enrolment.

The identification device 30 may be presented to the pharmacist forreading at the pharmacy system 16. Such reading may be performed at theone or more peripheral devices 22 though such is not required.Alternatively, or additionally, the identification device 30 may bepresented at the patient system 18 for retrieving information associatedwith the unique patient identifier and/or the unique prescriptionidentifiers. Such presentation may be made by way of an associatedperipheral device 22, though such is not required. The identificationdevice 30 may comprise additional identification information such as,but not limited to, a photo 34, identification information 36 (forexample, without limitation, a name, social security number, ID number,some combination thereof, or the like), physical description information38 (for example, without limitation, height, weight, hair color, eyecolor, some combination thereof, or the like), security devices 40 (forexample, without limitation, watermark, hologram, some combinationthereof, or the like), some combination thereof, or the like.

In exemplary embodiments, the same or similar identification device 30may be provided to each pharmacist and/or healthcare provider followingsuccessful enrollment. The identification device 30 may compriseidentification information and unique identifiers specific to thepharmacist and/or healthcare provider. The identification devices 30 maybe presented to the pharmacist systems 16 and/or the healthcare providersystems 20. Such presentation may be made by way of peripheral devices22, though such is not required.

FIG. 6 illustrates an exemplary telehealth embodiment of the system 10.The healthcare provider system 20 may comprise certain telehealthfeatures, subsystems, and/or components such as, but not limited to,telephones, text messaging systems, email systems, VOIP systems, webcams, cameras, video conferencing systems, microphones, speakers,electronic displays, computers, tablets, smartphones, some combinationthereof, or the like. The patient system 18 may comprise certaintelehealth features, subsystems and/or components such as, but notlimited to, telephones, text messaging systems, email systems, VOIPsystems, web cams, cameras, video conferencing systems, microphones,speakers, electronic displays, computers, tablets, smartphones, somecombination thereof, or the like. Electronic communication may beestablished between the patient and the healthcare provider by way ofone or more networks 14.

The telehealth consultation may be arranged and/or provided by way ofthe telehealth module 42, though such is not required. The telehealthconsultation may comprise audio and/or video components. The telehealthconsultation may result in the prescription of one or more medicationsby way of a new prescription, a refill, some combination thereof, or thelike.

Before, during, or after the telehealth consultation, evidence may bepresented to and/or gathered by the healthcare provider. In exemplaryembodiments, the evidence may comprise one or more images, videos, orthe like of an injury or other condition. Alternatively, oradditionally, the evidence may comprise test results, medical imagingresults, self-reported symptoms, some combination thereof, or the like.The evidence may be related to the symptoms, diseases, conditions, orthe like related to the prescription of medications.

The evidence may be uploaded to the patient prescription database 12 asdescribed herein. In exemplary embodiments, the evidence may be uploadedto the same electronically partitioned area as the associateprescription(s). The evidence may remain in the electronicallypartitioned area for the same time as the associate prescription(s),though such is not required. For example, without limitation, theevidence may remain in the patient prescription database 12 for a longerperiod of time or indefinitely.

Before or after upload, the evidence may be associated with one or moreprescriptions prescribed, refilled, or the like by the healthcareprovider in conjunction with the consultation. The evidence may beretrieved from the patient prescription database 12 in conjunction withthe retrieval of prescriptions as detailed herein.

The evidence may be retrieved when the prescription is accessed toverify the patient's identity. Alternatively, or additionally, theevidence may be accessed to compare a patient's current presentationwith a former presentation for purposes of evaluating the adequacy of aprescription, the potential for fraud, mistake, and/or misunderstanding,the need for a refill, the need for further treatment, some combinationthereof, or the like.

For example, without limitation, the patient may present with an ongoingskin condition. A picture of the skin condition may be uploaded asevidence with the prescription. The dispensing pharmacy may access theevidence to verify that the person to whom the pharmacy is dispensingthe medication is indeed the patient. Alternatively, or additionally,the healthcare provider may access the evidence to compare the evidenceagainst the patient's current symptoms to see if a refill, a differentdose, an alternative medication, or the like are warranted.Alternatively, or additionally, the healthcare provider or another partymay access the evidence to verify cause for prescribing and dispensingthe medication.

As another example, without limitation, if the evidence associated witha narcotics prescription shows significant bruising around themidsection, but the party asserting themselves to be the patient fordispensation of the medication shows no such bruising a determinationmay be made that the prescription was obtained fraudulently, is nolonger needed, some combination thereof, or the like. As anotherexample, again without limitation, evidence of the same injury may beprovided for multiple prescription for narcotics from multiplehealthcare providers, tending to indicate fraud. Upon review of suchmultiple prescriptions for narcotics for the same injury, the healthcareprovider and/or the pharmacist may determine that fraud may beoccurring.

The patient prescription database 12 may be contained within a singleelectronic storage device or spread across multiple, locally or remotelylocated electronic storage devices.

FIG. 7 is an exemplary user interface 54 for selecting a dispensingpharmacy 60. Pharmacies 60 associated with pharmacy systems 16 incommunication with the patient prescription database 12 may beidentified. In exemplary embodiments, pharmacies 60 within apredetermined or variable geographic distance from a location 62 of thepatient system 18 and or another location 62 specified at the patientsystem 18 may be identified. Such pharmacies 60 may be shown on a map 56in their approximate geographic location. The location 62 may also beshown on the map 56. The location may be determined by a location deviceat the patient system 18, manual entry, preprogramming, some combinationthereof, or the like.

A listing of the pharmacies 60 may be generated at the same or adifferent screen 58. The listing may identify each of the pharmacies 60,their approximate geographic distance from the location 62, theavailability of one or more prescriptions associated with the patient,and the approximate wait time for pick up and/or delivery (ifavailable). The location of the pharmacy 60, and therefore the distancefrom the location specified by the patient system 18, may be determinedby determined by a location device at the pharmacy system 16, manualentry, preprogramming, some combination thereof, or the like. Inexemplary embodiments, the time for a prescription to be filled and/ordelivered may be determined, at least in part, by the systems shown anddescribed in U.S. Pat. No. 9,659,269 issued May 23, 2017, thedisclosures of which are hereby incorporated by reference as if fullyrestated herein.

Any embodiment of the present invention may include any of the featuresof the other embodiments of the present invention. The exemplaryembodiments herein disclosed are not intended to be exhaustive or tounnecessarily limit the scope of the invention. The exemplaryembodiments were chosen and described in order to explain the principlesof the present invention so that others skilled in the art may practicethe invention. Having shown and described exemplary embodiments of thepresent invention, those skilled in the art will realize that manyvariations and modifications may be made to the described invention.Many of those variations and modifications will provide the same resultand fall within the spirit of the claimed invention. It is theintention, therefore, to limit the invention only as indicated by thescope of the claims.

Certain operations described herein may be performed by one or moreelectronic devices. Each electronic device may comprise one or moreprocessors, electronic storage devices, executable softwareinstructions, and the like configured to perform the operationsdescribed herein. The electronic devices may be general purposecomputers or specialized computing devices. The electronic devices maybe personal computers, smartphone, tablets, databases, servers, or thelike. The electronic connections described herein may be accomplished bywired or wireless means. The computerized hardware, software,components, systems, steps, methods, and/or processes described hereinmay serve to improve the speed of the computerized hardware, software,systems, steps, methods, and/or processes described herein.

What is claimed is:
 1. A system for providing world-wide access totelehealth prescribed medications, said system comprising: a healthcareprovider system comprising a telehealth component configured tofacilitate a remote health consultation, said healthcare provider systemconfigured to generate electronic prescriptions; a patient system inelectronic communication with the healthcare provider system andcomprising a telehealth component configured to facilitate the remotehealth consultation; a patient prescription database in electroniccommunication with the healthcare provider system and the patientsystem, said patient prescription database comprising electronicprescriptions received from the healthcare provider system, wherein eachof the electronic prescriptions is associated with a unique patientidentifier; a number of pharmacy systems, each positioned at a differentgeographic location around the world and in electronic communicationwith the prescription database; software instructions associated withthe prescription database, which when executed, configure one or moreprocessors to: receive a unique patient identifier from a particular oneof the number of pharmacy systems or the patient system; receive aunique pharmacist identifier from the particular pharmacy system; verifythat the received unique patient identifier matches a stored patientidentifier, and that the received unique pharmacist identifier matches astored pharmacist identifier and then: display, at the particularpharmacy system, each of the electronic prescriptions associated withthe received unique patient identifier; receive a user selection of oneof the displayed prescriptions from the particular pharmacy systems;receive, from the particular pharmacy system, dispensation informationcomprising an amount of medication dispensed, a time and date ofdispensation, and a reason for dispensation for the selectedprescription; and update, at the prescription database, the selectedprescription with the dispensation information, wherein the dispensationinformation is associated with the received unique pharmacistidentifier.
 2. The system of claim 1 wherein: the telehealth componentof the of the healthcare provider system comprises a video camera and amicrophone; and the telehealth component of the of the patient systemcomprises a video camera and a microphone.
 3. The system of claim 1wherein: the telehealth component of the of the healthcare providersystem comprises a telephone; and the telehealth component of the of thepatient system comprises a telephone.
 4. The system of claim 1 wherein:each of the electronic prescriptions is associated with a unique patientidentifier and evidence supporting the electronic prescription; saidpatient prescription database is configured to display said evidencesupporting the electronic prescription at the particular pharmacysystem; and said evidence comprises images or videos of symptomsassociated with a disease or condition for which the associatedelectronic prescription was prescribed to treat.
 5. The system of claim1 further comprising: additional software instructions associated withthe prescription database, which when executed, configure the one ormore processors to: determine a geographic location associated with thereceived unique pharmacist identifier; determine one or more languagesassociated with the determined geographic location; and provide, by wayof a translation module in electronic communication with theprescription database, a machine translation of the retrieved electronicprescriptions into the determined language.
 6. The system of claim 1wherein: the amount of medication dispensed is less than a full amountavailable under the associated electronic prescription; and the reasonfor dispensation is selected from pre-determined options comprising lostmedication, insufficient medication, and theft of medication.
 7. Thesystem of claim 6 further comprising: additional software instructionsassociated with the prescription database, which when executed,configure the one or more processors to: verify the received particularunique patient identifier against a list of accepted unique patientidentifiers stored at the prescription database; and remove theparticular unique patient identifier from the list of accepted uniquepatient identifiers when a particular one of the reasons fordispensation is received in association with the particular uniquepatient identifier with a frequency above a predetermined threshold. 8.The system of claim 6 wherein: each electronic prescription isassociated with an expiration date; and said patient prescriptiondatabase comprises additional software instructions, which whenexecuted, configure the one or more processors to: determine a currentdate; and remove prescriptions associated with an expiration date priorto the current date.
 9. The system of claim 8 further comprising:additional software instructions associated with the prescriptiondatabase, which when executed, configure the one or more processors toautomatically associate a default expiration date with each electronicprescription, wherein said default expiration date is specific to aclass of drug for the medication associated with the prescription. 10.The system of claim 1 further comprising: additional softwareinstructions stored at the prescription database, which when executed,configure the one or more processors to: provide read-only access at aparticular one of the number of patient systems where a unique patientidentifier matching one of the unique patient identifiers stored at thepatient prescription database is received from the particular patientsystem, wherein said read-only access is limited to electronicprescriptions associated with the received unique patient identifier;provide write-access at a particular one of the number of pharmacysystems with respect to the dispensation information where a uniquepharmacist identifier matching a unique pharmacist identifier stored atthe patient prescription database is received from the particularpharmacy system, wherein said write-access is limited to dispensationinformation for electronic prescriptions associated with the receivedunique patient identifier; and provide write-access at a particular oneof the number of healthcare provider systems where a unique healthcareprovider identifier matching one of the unique healthcare provideridentifiers stored at the patient prescription database has beenreceived from the particular healthcare provider system, wherein saidwrite-access is limited to electronic prescriptions associated withunique patient identifiers associated with the received uniquehealthcare providers.
 11. The system of claim 1 wherein: each of theunique patient identifiers comprise a user id and password; and each ofthe unique pharmacist identifiers comprise a user id and password. 12.The system of claim 1 wherein: the electronic prescriptions areelectronically partitioned by patient identifier such that allelectronic prescriptions associated with a given one of the patientidentifiers is stored at separate electronic storage areas.
 13. Thesystem of claim 12 wherein: each of the electronic prescriptions isassociated with a unique patient identifier and evidence supporting theelectronic prescription; said patient prescription database isconfigured to display said evidence supporting the electronicprescription at the particular pharmacy system; and the evidenceassociated with a given electronic prescription is stored within thesame electronic storage area as the associated electronic prescription.14. The system of claim 1 further comprising: a telehealth moduleconfigured to accept electronic requests from the patient systems for atelehealth consultation and transmit an electronic notification to thehealthcare provider system with a proposed date and time for thetelehealth consultation comprising an option to accept the proposedtelehealth consultation.
 15. A method for providing world-wide access totelehealth prescribed medications, said method comprising the steps of:establishing an electronic connection between a particular one of anumber of healthcare provider systems and a particular one of a numberof patient systems; performing a telehealth consultation by way of theparticular healthcare system and the particular patient system;uploading an electronic prescription resulting from the telehealthconsultation from the particular healthcare system to a prescriptiondatabase, wherein said electronic prescription comprises a prescribedmedication, a unique patient identifier, and a number of prescribedunits of said prescribed medication; associating the uploaded electronicprescription with the unique patient identifier; providing a number ofpharmacy systems in electronic communication with the prescriptiondatabase, wherein each of said number of pharmacy systems are located atvarious geographic locations; receiving, from a particular one of thenumber of pharmacy systems, the unique patient identifier; receiving,from the particular pharmacy system, a unique pharmacist identifier;displaying, at the particular pharmacy system, each of the electronicprescriptions stored at the patient prescription database which areassociated with the unique patient identifier; receiving, from theparticular pharmacy system, dispensation information comprising anamount of medication dispensed, a time and date of dispensation, and areason for dispensation; updating, at the prescription database, theelectronic prescription with the dispensation information; associating,at the prescription database, the dispensation information with thereceived unique pharmacist identifier.
 16. The method of claim 15wherein: the amount of medication dispensed is less than the number ofprescribed units; and the step of updating the electronic prescriptionwith the dispensation information comprises subtracting the amount ofmedication dispensed from the number of prescribed units.
 17. The methodof claim 15 further comprising the steps of: uploading evidence relatedto the electronic prescription from the particular healthcare system tothe prescription database; associating the uploaded evidence with theuploaded electronic prescription at the prescription database;displaying, at the particular pharmacy system, evidence associated withthe displayed electronic prescriptions; receiving a number of additionalelectronic prescriptions from the number of healthcare provider systems,wherein each of the number of additional electronic prescriptions isassociated with one of a number of unique patient identifiers; receivingevidence from the number of healthcare provider systems, wherein eachitem of evidence received is associated with one of the number ofadditional electronic prescriptions; and electronically partitioning thepatient prescription database by unique patient identifier such that allof the electronic prescriptions and evidence associated with a givenunique patient identifier is electronically separated from all otherelectronic prescriptions and evidence associated with other uniquepatient identifiers.
 18. The method of claim 15 further comprising thesteps of: providing, at the patient systems, read-only access toelectronic prescriptions stored at the patient prescription database andassociated with the unique patient identifier upon receipt of the uniquepatient identifier; providing, at the pharmacy systems, write access todispensation information associated with electronic prescriptions storedat the patient prescription database and associated with the uniquepatient identifier upon receipt of the unique patient identifier and theunique pharmacist identifier; and providing, at the healthcare providersystems, write access to electronic prescriptions stored at the patientprescription database and associated with the unique patient identifierupon receipt of the unique patient identifier and a unique healthcareprovider identifier.
 19. The method of claim 15 further comprising thesteps of: verifying, at the prescription database, that the uniquepatient identifier matches a stored unique patient identifier;verifying, at the prescription database, that the unique pharmacistidentifier matches a stored unique pharmacist identifier; and verifying,at the prescription database, that the unique healthcare provideridentifier matches a stored unique healthcare provider identifier.
 20. Asystem for providing world-wide access to evidence supported, telehealthprescribed medications, said system comprising: a number of patientsystems, each comprising a camera, a microphone, and a speaker; a numberof healthcare provider systems, each comprising a camera, a microphone,and a speaker, wherein each of said number of healthcare providersystems are configured to selectively establish electronic communicationwith one of the number of patient systems to conduct a videographic ortelephonic health consultation for a patient; a number of pharmacysystems, each located at a separate geographic area around the world; apatient prescription database in electronic communication with each ofthe number of of healthcare provider systems and each of the number ofpharmacy systems, said patient prescription database comprising softwareinstructions, which when executed, configure one or more processors to:receive electronic prescriptions uploaded from the number of healthcareprovider systems, wherein each of the electronic prescriptions isassociated with a received unique patient identifier; receive evidenceuploaded from the number of healthcare provider systems, wherein eachitem of evidence is associated with one of the received electronicprescriptions; electronically partition the received electronicprescriptions and associated items of evidence by patient identifier;upon receipt and verification of a particular unique patient identifierfrom a particular one of the number of pharmacy systems: transmit allelectronic prescriptions associated with said particular unique patientidentifier to the particular pharmacy system for display; upon selectionof one of the transmitted electronic prescriptions, transmit evidenceassociated with the selected electronic prescription to the particularpharmacy system for display; receive from the particular pharmacy systemdispensation information associated with one of the transmittedelectronic prescriptions, said dispensation information comprising aselection of one of the transmitted electronic prescriptions, a uniquepharmacist identifier, an identification of items dispensed, and areason for dispensation; and update the one of the transmittedelectronic prescriptions with the dispensation information.